fix(agent): reject invalid output modes#50
Conversation
|
@coderabbitai review |
✅ Action performedReview finished.
|
|
Warning Review limit reached
Next review available in: 59 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
Thanks @JerryNee! 🙏 #14 introduces a shared Great catch on the gap — hope to see more PRs from you! 🚀 |
2 participants
Summary
testsprite agent ... --output <mode>against the supportedjson|textmodesVALIDATION_ERRORshape instead of silently treating unsupported modes as textagent listBefore
testsprite agent list --output yamlexited 0 and printed text output.After
testsprite agent list --output yamlexits 5 with:Verification
npm test -- src/commands/agent.test.tsnpm run lintnpm run typechecknpm testnpm run buildnode dist/index.js agent list --output yaml